<rss version="2.0" xmlns:wfw="http://wellformedweb.org/CommentAPI/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:trackback="http://madskills.com/public/xml/rss/module/trackback/">
    <channel>
        <title>Business Analyst Community &amp; Resources | Modern Analyst</title> 
        <link>https://modernanalyst.com</link> 
        <description>RSS feeds for Business Analyst Community &amp; Resources | Modern Analyst</description> 
        <ttl>60</ttl> <item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/7080/Agile-vs-Traditional-Business-Analysis-Which-Delivers-Better-ROI.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=7080</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=7080&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Agile vs. Traditional Business Analysis: Which Delivers Better ROI?</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/7080/Agile-vs-Traditional-Business-Analysis-Which-Delivers-Better-ROI.aspx</link> 
    <description>In today&amp;rsquo;s fast-moving business world, agility is everything. Companies are under pressure to move quickly, adapt to change, and deliver value faster than ever. That&amp;rsquo;s why when it comes to managing projects and analysing business needs, the way you work can make or break your success. For most teams, the big question is: should we go with Agile or stick to the more traditional, Waterfall-style approach? And more importantly which one drives better return on investment?
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Tue, 04 Nov 2025 05:09:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:7080</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/7041/Applying-Agile-Hybrid-Frameworks-in-Large-Projects.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=7041</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=7041&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Applying Agile &amp; Hybrid Frameworks in Large Projects</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/7041/Applying-Agile-Hybrid-Frameworks-in-Large-Projects.aspx</link> 
    <description>This article explores practical techniques that BAs can apply in large projects: how to prioritize backlogs when competing domains fight for attention, how to bridge Agile with Waterfall governance, how to contribute meaningfully in scaled frameworks, and how to use story mapping to ensure incremental delivery of real business value.
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Sun, 21 Sep 2025 04:01:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:7041</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6974/Making-Agile-Work-in-Complex-Systems-The-JTBD-Enhanced-User-Story-Framework.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6974</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6974&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Making Agile Work in Complex Systems:  The JTBD-Enhanced User Story Framework</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6974/Making-Agile-Work-in-Complex-Systems-The-JTBD-Enhanced-User-Story-Framework.aspx</link> 
    <description>This article presents a novel methodology that synergizes user stories with JTBD for complex projects. A thorough literature review is conducted, carefully highlighting the strengths, limitations, and overall benefits of each approach. Next, an integrated framework is introduced, featuring diagrams, examples, and a comparative table. A concise case example demonstrates practical application. In conclusion, implications, limitations, and future research directions are discussed, aiming to enhance requirement clarity and alignment in complex software development.
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Sun, 27 Jul 2025 23:07:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6974</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6681/Product-Roadmap-Why-and-How.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6681</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6681&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Product Roadmap: Why and How</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6681/Product-Roadmap-Why-and-How.aspx</link> 
    <description>Do we really need a product roadmap? Why? How do we go about creating a product roadmap? What are a few of the best practices? This article sheds light on these &amp;#39;planning questions&amp;#39; which probably every product team has come across. Especially agile teams. Let&amp;#39;s quickly review first what is a product roadmap and then review top three concerns and their solutions when it comes to building it.
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Mon, 10 Feb 2025 05:09:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6681</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6602/Requirements-vs-User-Stories-Which-Are-Better.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6602</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6602&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Requirements vs. User Stories: Which Are Better?</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6602/Requirements-vs-User-Stories-Which-Are-Better.aspx</link> 
    <description>As someone who has worked as a business analyst for more years than I care to admit, one of the most common questions I get is: &amp;ldquo;Which is better, requirements or user stories?&amp;rdquo; If only the answer were that simple! The truth is, there isn&amp;rsquo;t a clear winner, because they serve different purposes and complement each other in ways that are essential to a successful project.

I&amp;rsquo;ve seen teams try to use only one of the two and miss critical aspects of a project. And I&amp;rsquo;ve seen projects where both were used in tandem, leading to smooth communication, aligned expectations, and a final product that delighted both users and stakeholders. Let me walk you through why both requirements and user stories are important tools in our arsenal as business analysts&amp;mdash;and why, as practitioners, we should never limit ourselves to just one.
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Mon, 16 Sep 2024 00:29:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6602</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6554/The-Essential-Role-of-Business-Analysts-in-Agile-Software-Development.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6554</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6554&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>The Essential Role of Business Analysts in Agile Software Development</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6554/The-Essential-Role-of-Business-Analysts-in-Agile-Software-Development.aspx</link> 
    <description>The Essential Role of Business Analysts in Agile Software Development: An In-Depth Analysis

With the rise of Agile Software Development Life Cycle (SDLC) and methodologies such as Scrum, there has been a notable shift in the staffing dynamics of software development teams. Many organizations have adopted a developer-centric approach, often excluding the dedicated role of the Business Analyst (BA). This trend is based on the misconception that Agile teams can function optimally with only developers, who are expected to take on additional responsibilities such as requirements elicitation and management. However, this practice is fundamentally flawed and can lead to significant challenges and inefficiencies. This article explores why the role of the Business Analyst remains crucial in Agile teams and software development in general, highlighting the risks and pitfalls of sidelining this essential function.



The Misconception of Developer-Centric Teams

Agile methodologies emphasize cross-functional teams, where members collectively share responsibilities. While this collaborative approach is beneficial, it does not eliminate the need for specialized roles. Here are some reasons why relying solely on developers for business analysis tasks is problematic:


 
 Developers Prefer Coding Over Requirements Management -&amp;nbsp;Developers are primarily trained and motivated to write code. Activities such as requirements elicitation, documentation, and stakeholder communication are often seen as secondary tasks. Without a dedicated BA, these critical activities may be overlooked or inadequately performed. According to Forrester Research, teams that lack dedicated BAs often experience gaps in requirement clarity, leading to increased project risks and rework (Forrester Research, 2019).
 
 
 Skill Set Disparities -&amp;nbsp;The skill sets required for effective business analysis&amp;mdash;such as analytical thinking, communication, and domain knowledge&amp;mdash;are different from those needed for software development. It is rare to find individuals who excel in both areas, and those who do are often highly sought after and expensive. The International Institute of Business Analysis (IIBA) highlights that &amp;quot;business analysis skills are crucial for understanding the underlying business needs and translating them into actionable requirements&amp;quot; (IIBA, 2017).
 
 
 Cost Implications -&amp;nbsp;Hiring individuals who can perform both development and business analysis tasks proficiently can be costly. These multi-skilled practitioners are few and far between, and their salaries can significantly impact the project budget. The Project Management Institute (PMI) reports that &amp;quot;the cost of hybrid professionals can be prohibitive, often outweighing the benefits&amp;quot; (PMI, 2018).
 


The Critical Role of Business Analysts

Business Analysts bring unique value to software development projects, especially within Agile frameworks. Their contributions ensure that the development process aligns with business goals and stakeholder needs.


 
 Bridging the Gap Between Stakeholders and Developers -&amp;nbsp;BAs act as intermediaries who translate business needs into technical requirements. This translation is crucial for ensuring that the development team understands what needs to be built and why. According to a study by the International Institute of Business Analysis (IIBA), &amp;quot;the role of the BA is pivotal in ensuring that project requirements are clearly defined and understood by all stakeholders&amp;quot; (IIBA, 2017).
 
 
 Facilitating Communication -&amp;nbsp;Effective communication is a cornerstone of Agile methodologies. BAs excel in facilitating discussions between stakeholders and the development team, ensuring that all parties are aligned. This reduces the risk of miscommunication and ensures that the project stays on track. A report by Gartner notes that &amp;quot;effective communication facilitated by BAs leads to better project outcomes and higher stakeholder satisfaction&amp;quot; (Gartner, 2020).
 
 
 Requirements Elicitation and Management -&amp;nbsp;BAs employ various techniques to gather requirements, such as interviews, workshops, and document analysis. They ensure that requirements are comprehensive, clear, and testable. A report by Forrester Research highlights that &amp;quot;projects with dedicated BAs have higher success rates due to better requirements management&amp;quot; (Forrester Research, 2019).
 
 
 Continuous Improvement&amp;nbsp;- In Agile environments, BAs contribute to continuous improvement by constantly refining requirements based on feedback from stakeholders and end-users. This iterative approach ensures that the final product meets user expectations and delivers value. The Agile Manifesto emphasizes the importance of responding to change, and BAs play a critical role in this by managing evolving requirements (Beck et al., 2001).
 
 
 Domain Expertise -&amp;nbsp;BAs often possess deep domain knowledge, which is essential for understanding the context in which the software will be used. This expertise allows them to identify potential issues and opportunities that may not be apparent to developers. The IIBA states that &amp;quot;domain expertise enables BAs to provide valuable insights that enhance the relevance and usability of the final product&amp;quot; (IIBA, 2017).
 


Case Studies and Industry Insights

Numerous case studies and industry insights reinforce the importance of BAs in Agile teams. Here are a few examples:


 
 Case Study: Financial Services Company -&amp;nbsp;A financial services company implemented an Agile transformation but initially excluded BAs from their teams. They soon realized that developers struggled with gathering and managing requirements, leading to project delays and increased rework. By reintegrating BAs into their teams, the company saw a significant improvement in project outcomes and stakeholder satisfaction. This case highlights the critical role of BAs in managing requirements and ensuring project success (Financial Services Case Study, 2018).
 
 
 Industry Insight: Gartner -&amp;nbsp;Gartner emphasizes the importance of BAs in Agile teams, stating that &amp;quot;organizations that include BAs in their Agile teams are more likely to achieve project success and deliver high-quality products&amp;quot; (Gartner, 2020). They recommend that organizations leverage the unique skills of BAs to enhance collaboration and ensure that business objectives are met.
 


Addressing Common Objections

Despite the clear benefits, some organizations remain skeptical about the necessity of BAs in Agile teams. Here are some common objections and counterarguments:


 
 Objection: Agile Teams Should Be Self-Sufficient -&amp;nbsp;While Agile teams are designed to be self-sufficient, this does not mean that every team member should perform all roles. Specialization enhances efficiency and quality. BAs bring specialized skills that complement those of developers, leading to better overall team performance. According to the Scrum Guide, &amp;quot;cross-functional teams are essential, but roles within the team can be specialized to enhance productivity&amp;quot; (Schwaber &amp;amp; Sutherland, 2020).
 
 
 Objection: BAs Slow Down the Process&amp;nbsp;- Some believe that involving BAs adds unnecessary steps and slows down the development process. However, well-defined and managed requirements actually speed up development by reducing misunderstandings and rework. BAs streamline the process by ensuring that requirements are clear and actionable from the outset. A study by McKinsey &amp;amp; Company found that &amp;quot;effective requirements management can reduce project timelines by up to 20%&amp;quot; (McKinsey &amp;amp; Company, 2019).
 
 
 Objection: Developers Can Handle Requirements&amp;nbsp;- While some developers may have the skills to handle requirements, it is not their primary focus. Splitting their attention between coding and requirements management can lead to burnout and decreased productivity. Dedicated BAs allow developers to focus on what they do best&amp;mdash;writing high-quality code. The Standish Group&amp;rsquo;s CHAOS Report states that &amp;quot;projects are more successful when developers can concentrate on coding, leaving requirements management to BAs&amp;quot; (Standish Group, 2018).
 


The Future of Business Analysis in Agile

As Agile methodologies continue to evolve, the role of the BA will become even more critical. Here are some emerging trends that highlight the importance of BAs:


 
 Increased Focus on User Experience (UX)&amp;nbsp;- BAs will play a crucial role in enhancing UX by ensuring that user needs and feedback are integrated into the development process. Their ability to gather and analyze user requirements will be essential for creating intuitive and user-friendly software. As UX becomes a focal point in product development, the analytical skills of BAs will be invaluable (Nielsen Norman Group, 2020).
 
 
 Data-Driven Decision Making&amp;nbsp;- The rise of data analytics will require BAs to incorporate data-driven insights into their analysis. BAs will need to work closely with data scientists to understand and leverage data for better decision-making. This collaboration will enhance the relevance and accuracy of requirements (Davenport &amp;amp; Harris, 2017).
 
 
 Agile at Scale&amp;nbsp;- As organizations adopt Agile at scale, the need for effective requirements management will increase. BAs will be essential for coordinating requirements across multiple teams and ensuring that the overall vision and goals are maintained. Scaling Agile requires robust communication and alignment, which BAs are well-equipped to provide (SAFe, 2020).
 
 
 Hybrid Roles&amp;nbsp;- While the BA role will remain distinct, there will be an increase in hybrid roles where BAs possess some technical skills. This will enhance their ability to collaborate with developers and contribute to technical discussions, while still focusing on their core responsibilities. The demand for versatile professionals who can bridge the gap between business and technology will grow (World Economic Forum, 2020).
 


Conclusion

The exclusion of Business Analysts from Agile teams is a short-sighted practice that can lead to numerous challenges and inefficiencies. BAs bring unique skills and expertise that are essential for successful software development. They bridge the gap between stakeholders and developers, facilitate effective communication, manage requirements, and contribute to continuous improvement. By recognizing the value of BAs and integrating them into Agile teams, organizations can enhance their project outcomes and deliver high-quality software that meets business needs.

As Agile methodologies continue to evolve, the role of the BA will only become more critical. Organizations that embrace this role and leverage the skills of BAs will be better positioned to succeed in the fast-paced and ever-changing world of software development.

What do you think?


Author: Maria Santos, Senior Systems Analyst

Maria Santos is a seasoned systems analyst with a passion for unraveling complex technological puzzles. Armed with a background in computer science and a keen eye for detail, Maria thrives in the dynamic world of software development, where she combines technical expertise with creative problem-solving to deliver innovative solutions.&amp;nbsp;&amp;nbsp;With years of experience collaborating with multidisciplinary teams, Maria has honed her ability to navigate ambiguity and translate disparate stakeholder perspectives into cohesive system designs. Her dedication to continuous learning and adaptability has enabled her to stay at the forefront of emerging technologies and industry best practices.

Outside of her professional endeavors, Maria is an avid reader and aspiring writer, with a penchant for exploring diverse topics ranging from technology trends to personal development. She is excited to share her insights and experiences with readers, hoping to inspire and empower others on their own journeys in the ever-evolving landscape of technology.


References:


 International Institute of Business Analysis (IIBA), &amp;quot;The Role of the Business Analyst,&amp;quot; 2017.
 Forrester Research, &amp;quot;The Value of Requirements Management,&amp;quot; 2019.
 Gartner, &amp;quot;The Importance of Business Analysts inAgile Teams,&amp;quot; 2020.
 Project Management Institute (PMI), &amp;quot;The Cost of Hybrid Professionals,&amp;quot; 2018.
 McKinsey &amp;amp; Company, &amp;quot;Effective Requirements Management,&amp;quot; 2019.
 Standish Group, &amp;quot;CHAOS Report,&amp;quot; 2018.
 Beck et al., &amp;quot;The Agile Manifesto,&amp;quot; 2001.
 Schwaber &amp;amp; Sutherland, &amp;quot;The Scrum Guide,&amp;quot; 2020.
 Nielsen Norman Group, &amp;quot;UX in Product Development,&amp;quot; 2020.
 Davenport &amp;amp; Harris, &amp;quot;Competing on Analytics: The New Science of Winning,&amp;quot; 2017.
 Scaled Agile Framework (SAFe), &amp;quot;Agile at Scale,&amp;quot; 2020.
 World Economic Forum, &amp;quot;Future of Jobs Report,&amp;quot; 2020.

</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Mon, 15 Jul 2024 00:51:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6554</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6515/Three-Critical-Mistakes-with-User-Stories.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6515</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6515&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Three Critical Mistakes with User Stories</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6515/Three-Critical-Mistakes-with-User-Stories.aspx</link> 
    <description>Navigating agile software development requires awareness of common pitfalls with user stories. Avoiding the mistakes of over-reliance on user stories, treating them as specifications, and not defining user roles clearly can significantly improve your process. By integrating diverse documentation techniques like wireframes, prototypes, and use case specifications alongside user stories, teams can achieve a more holistic and detailed understanding of requirements. This approach fosters collaboration, clarity, and alignment, ultimately leading to more successful software solutions.
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Mon, 27 May 2024 02:47:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6515</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6453/Unlocking-the-Potential-The-Business-Analysts-Role-in-Agile-Teams.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6453</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6453&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Unlocking the Potential: The Business Analyst&#39;s Role in Agile Teams</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6453/Unlocking-the-Potential-The-Business-Analysts-Role-in-Agile-Teams.aspx</link> 
    <description>Much like a coach orchestrating a championship-winning sports team, the BA plays a multifaceted role in ensuring the effectiveness and efficiency of agile initiatives. They are tasked with guiding the team through the intricacies of information gathering, requirements elicitation, analysis, and prioritization, aligning disparate perspectives towards a common goal. Moreover, the BA acts as a catalyst for collaboration, fostering an environment where diverse skill sets converge to deliver tangible outcomes.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 25 Feb 2024 05:03:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6453</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6289/Accelerated-Design-Sprints.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6289</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6289&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Accelerated Design Sprints</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6289/Accelerated-Design-Sprints.aspx</link> 
    <description>Design Sprints are a 5-day process to create and test new ideas. They can be used to explore new features for an existing product, or test a new product.&amp;nbsp;&amp;nbsp;In this article I will:&amp;nbsp;Describe Design Sprints,&amp;nbsp;Explain the advantages and limitations of Design Sprints,&amp;nbsp;Describe &amp;lsquo;Accelerated Design Sprints&amp;rsquo; &amp;ndash; which are a more streamlined process,&amp;nbsp;Walkthrough how to run an &amp;lsquo;Accelerated Design Sprint&amp;rsquo;.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 02 Jul 2023 21:59:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6289</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6247/Application-of-Minimalism-to-MVP.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6247</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6247&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Application of Minimalism to MVP</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6247/Application-of-Minimalism-to-MVP.aspx</link> 
    <description>Minimalist, Minimum Viable Product (MVP), Minimalism, Light Weight Travel? What is the common thread among all these? Well, the topic of minimalism has been there on my mind for long, so has been the related work topic, MVP. Let&amp;#39;s delve into seeing how we can apply the concepts from minimalism into MVP.
Minimalism is a lifestyle and a trending term for several years now. Minimalism has many definitions for different people. So what is minimalism?
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Sun, 02 Apr 2023 04:01:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6247</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6225/How-to-Change-the-World-by-Infusing-Sustainability-Into-All-Your-Agile-User-Stories.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6225</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6225&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>How to Change the World by Infusing Sustainability Into All Your Agile “User Stories”</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6225/How-to-Change-the-World-by-Infusing-Sustainability-Into-All-Your-Agile-User-Stories.aspx</link> 
    <description>Product Owners and Managers can now prioritize based on impact to the governance and transparency of their company, the environmental impact the solution will have, and even the social impacts on their company and the world.

Sometimes it may be difficult as a user story should not at first have a solution in mind, but as with some of the examples below, there can be known impacts up front, and you can always feel free to update the &amp;ldquo;impact&amp;rdquo; statement once a solution and requirements are identified.

&amp;nbsp;
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Mon, 20 Feb 2023 03:14:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6225</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6214/As-a-BA-I-Want-to-Write-a-User-Story.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6214</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6214&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>As a BA, I Want to Write a User Story…</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6214/As-a-BA-I-Want-to-Write-a-User-Story.aspx</link> 
    <description>This thought recently popped into my mind when someone asked me what template to follow when writing a user story. Perhaps you have encountered or asked this question before.&amp;nbsp;As a Business Analyst,&amp;nbsp;I want to use a template to write a user story, so that, my team will understand the requirements.&amp;nbsp;&amp;nbsp;Do formats and templates really matter?
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Sun, 29 Jan 2023 23:22:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6214</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3702/What-is-the-Agile-Practice-in-Your-Project-Part-2.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3702</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3702&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>What is the Agile Practice in Your Project? (Part 2)</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3702/What-is-the-Agile-Practice-in-Your-Project-Part-2.aspx</link> 
    <description>I hope the above two examples give you an idea about how different the projects use agile principles based on the nature of the project. And I believe this would give you some tips if want to adjust the existing agile practice in your project too. So, the BA&amp;rsquo;s who have not worked in agile projects before, now you know how the real world agile projects are&amp;hellip;.
</description> 
    <dc:creator>dhanug01</dc:creator> 
    <pubDate>Sun, 06 Nov 2022 21:42:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3702</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3701/What-is-the-Agile-Practice-in-Your-Project-Part-1.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=3701</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=3701&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>What is the Agile Practice in Your Project? (Part 1)</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/3701/What-is-the-Agile-Practice-in-Your-Project-Part-1.aspx</link> 
    <description>If you surf the internet for &amp;lsquo;agile project methodology&amp;rdquo;, you may get lots of web pages explaining a similar set of activities which are /should be followed in Agile projects.&amp;nbsp;&amp;nbsp;Unless you have working experience in an agile project environment, you may imagine what a well-defined and smooth process the agile projects have!!&amp;nbsp;

What if you have really worked on an agile project, would you have the same perspective? Especially if you are a Business Analyst or an Iteration Manager&amp;hellip;. ? Those BA&amp;rsquo;s and IM&amp;rsquo;s&amp;hellip; I know what your answer is and the long explanation about your agile project experience is.. I can imagine even your annoyed faces &amp;hellip;
</description> 
    <dc:creator>dhanug01</dc:creator> 
    <pubDate>Sun, 30 Oct 2022 19:07:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:3701</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6109/4-Levels-of-User-Stories-for-Information-Systems.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6109</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6109&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>4 Levels of User Stories for Information Systems</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6109/4-Levels-of-User-Stories-for-Information-Systems.aspx</link> 
    <description>The objective of this article is to help business analysts capture functional requirements for an information system as User Stories. It discusses four levels of story. The first two levels represent business context. Levels three and four involve functional detail needed by developers and testers to deliver stories at those levels.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Mon, 03 Oct 2022 01:18:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6109</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6093/User-Stories-vs-Use-Cases.aspx#Comments</comments> 
    <slash:comments>5</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6093</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6093&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>User Stories vs Use Cases</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6093/User-Stories-vs-Use-Cases.aspx</link> 
    <description>What is Use Case?

Use case represents requirement in the form of user interactions with the system. Use case is always written with a specific user goal in mind. Each use case must contain an actor and verb. For example, &amp;lsquo;online buyer&amp;rsquo; is an actor and &amp;lsquo;add item to cart&amp;rsquo; is a verb.

A use case diagram represents the scope of all the features of the solution. It follows Unified Modelling Language&amp;trade; notation. Use case diagram comprises of several use cases that make the system altogether.

What is User Story?

User story is a business analysis artifact that is also user or persona driven. It describes the business need in the form of an ability user (or system) wants in the solution. It also must state why the ability is required and what the benefits of that ability are. It does not have any mandatory format though

User story is part of the (product/project) backlog. The backlog in turn contains user stories/tasks (requirements) in a linear fashion. Backlog is usually prioritized from high to low, additionally with a ranking when priorities are the same. When it is prioritized by business value of the tasks/stories in it, it is called managed backlog. In many projects, user stories are also represented visually as a user story map, which is a structured visualization of a backlog. User story map is a map of user stories that are transposed from a linear backlog, onto a visual working board.

Each of this concept is a detailed topic in itself. For the context of this article, I will limit it only at the introductory level. Let&amp;#39;s now look into differences and similarities between user stories and use cases.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 07 Aug 2022 08:37:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6093</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6022/What-is-the-Role-of-Project-Management-in-Agile-Software-Development.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=6022</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=6022&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>What is the Role of Project Management in Agile Software Development?</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/6022/What-is-the-Role-of-Project-Management-in-Agile-Software-Development.aspx</link> 
    <description>Agile project management describes an iterative approach that targets project management in a given setup. Usually, Agile project management focuses on subdividing large projects into smaller and more manageable tasks. These tasks are completed in some sort of short iterations that cover the entire project life cycle.&amp;nbsp;

If your team takes advantage of agile methodology, it will have higher chances of finishing the work faster, optimizing the workflow, and adapting to ever-changing project requirements.&amp;nbsp;

Agile project management enables your team to re-evaluate every single task it is undertaking. The Agile project management also lets the team members adjust in increments to keep up with the shifting customer landscape.
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Mon, 07 Mar 2022 03:04:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:6022</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5998/Why-Agile-Teams-Need-a-Team-Charter.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5998</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5998&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Why Agile Teams Need a Team Charter</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5998/Why-Agile-Teams-Need-a-Team-Charter.aspx</link> 
    <description>One of the most empowering aspects of the agile mindset is that fact that agile teams are generally self-organized verses the traditional command and control protocols of traditional project management. While there are several benefits to self-organizing teams, it can lead to failure if the team misses some key planning aspects during team formation. Agile chartering is key to executing successful agile initiatives. In general, agile charters consist of the project charter and a team charter. The project charter defines the project vision and objectives, while the team charter establishes how the team will work together and how they can incorporate agile values as the team collaborates. A team charter is especially critical when organizations are new to the process of incorporating agile frameworks into the organization as it will facilitate knowledge transfer and identify key learning opportunities. With that said, here are some key reasons agile teams need team charters.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Mon, 07 Feb 2022 00:01:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5998</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5962/Agile-Is-it-really-so-difficult-for-organizations.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5962</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5962&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Agile – Is it really so difficult for organizations?</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5962/Agile-Is-it-really-so-difficult-for-organizations.aspx</link> 
    <description>In my experience while working for different companies, I have seen that some organisations are learning to be agile while some pretend to be agile and others are not agile at all. While we are not here to talk about the last category (assuming they have a very good reason for not wanting to go agile), I would like to put down some challenges for organisations who are on their journey to becoming agile and for those who think they are agile but are possibly not. In this article, I am going to talk about my understanding of the plausible reasons why some organisations struggle to make it.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 12 Dec 2021 06:34:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5962</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5944/BA-Role-in-DevOps.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5944</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5944&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>BA Role in DevOps</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5944/BA-Role-in-DevOps.aspx</link> 
    <description>Is there something called as Agile BA or DevOps BA? Or is there a dedicated role such as &amp;lsquo;BA in DevOps&amp;rsquo;? How are Agile and DevOps related? How does BA role change or goes through metamorphosis, when it comes to DevOps?

One day, I got a corporate training enquiry and that is when I heard the term &amp;lsquo;Agile BA&amp;rsquo; for the first time. At that time, I had already worked on Agile projects yet nobody had referred to my role particularly as Agile BA. A thought came to my mind, what if there was a job post saying &amp;ldquo;looking for a &amp;lsquo;Waterfall BA&amp;rsquo;?&amp;rdquo; I even heard once: &amp;ldquo;With DevOps there is hardly any role a need for BA or PM&amp;rdquo;.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 28 Nov 2021 23:30:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5944</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5926/Doing-Business-Analysis-in-a-Hybrid-World.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5926</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5926&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Doing Business Analysis in a Hybrid World</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5926/Doing-Business-Analysis-in-a-Hybrid-World.aspx</link> 
    <description>One of the biggest challenges now facing business analysts is this: how do we successfully engage with stakeholders, elicit requirements, and have productive workshops and meetings, without actually meeting in person? The tried-and-tested methods of getting together in a collaborative space, using sticky notes and whiteboards, and bribing attendees with baked goods, are no longer quite so straightforward in a world where some or all of the stakeholders are on the far end of an internet connection.

There are several factors to consider when moving out of the purely physical realm as a business analyst.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 10 Oct 2021 05:04:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5926</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5848/Definition-of-Done--best-practice-to-succeed-in-software-projects.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5848</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5848&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Definition of Done - best practice to succeed in software projects</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5848/Definition-of-Done--best-practice-to-succeed-in-software-projects.aspx</link> 
    <description>How do we know when a user story is &amp;ldquo;done&amp;ldquo;? Can we say that the user story is done when it is coded and all acceptance tests for it are passed? Business representatives may say yes, but they do not know all the peculiarities of software development. So, such criteria as quality are not fully visible to them.

Or let&amp;rsquo;s have a look at another situation: a new feature that changed the business process was developed and tested according to the best software practices, but users struggle to use this feature because they are not sure about the changes this feature brings. Maybe a proper user manual or user training is needed in this case?

In this article, a simple, but very powerful technique which is called Definition of Done (DoD) is explained.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 30 May 2021 04:17:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5848</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5832/A-Business-Analysts-Experience-With-Scrum.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5832</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5832&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>A Business Analyst’s Experience With Scrum</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5832/A-Business-Analysts-Experience-With-Scrum.aspx</link> 
    <description>My experience taught me that the Scrum process framework is not the complete story. Scrum does not identify roles for the business analyst, system architect, tester, UI designer or deployment engineers. Instead, the work normally performed by these roles is performed by the development team or the product owner. It is possible that the Scrum development team includes people with all of these skills, but the problem is that all the development team work is performed within a sprint cycle. The only activity that Scrum identifies outside a sprint cycle is maintenance of a product backlog (and even then it is not documented as an activity in the Scrum framework).
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Mon, 03 May 2021 04:01:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5832</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5818/Writing-Foolproof-Acceptance-Criteria-as-a-Business-Analyst.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5818</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5818&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Writing Foolproof Acceptance Criteria as a Business Analyst</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5818/Writing-Foolproof-Acceptance-Criteria-as-a-Business-Analyst.aspx</link> 
    <description>Ever wondered how to write foolproof acceptance criteria? Or even wondered what a business analyst can do to ensure that requirements are testable? Acceptance criteria define the minimum requirements the solution must meet. A business analyst plays a key role in defining the tests around it. The acceptance tests can be at various levels of requirements detail. Starting from high-level requirements to detailed requirements. Let&amp;rsquo;s take a look at common challenges involved in this part of the world, along with a few ideas to overcome those.
</description> 
    <dc:creator>Swatipitre</dc:creator> 
    <pubDate>Sun, 25 Apr 2021 04:57:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5818</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5788/Whats-the-Point-of-Business-Events.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5788</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5788&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>What’s the Point of Business Events?</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5788/Whats-the-Point-of-Business-Events.aspx</link> 
    <description>A business event is something that happens, and when it happens it causes a pre-planned response by the business, or as we shall call it here, &amp;ldquo;the work&amp;rdquo;. One category of business events are the things that happen inside an adjacent system. The work is made aware that the business event has happened because each happening produces a flow of data to the work. A business event is a significant happening &amp;ndash; it is not just a mouse click. It is often a request for a service that your business provides, and the outcome is the provision of the service or product.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Mon, 22 Mar 2021 01:00:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5788</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5800/The-Art-of-Writing-Specifications-in-an-Agile-Ecosystem.aspx#Comments</comments> 
    <slash:comments>2</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5800</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5800&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>The Art of Writing Specifications in an Agile Ecosystem</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5800/The-Art-of-Writing-Specifications-in-an-Agile-Ecosystem.aspx</link> 
    <description>Writing functional specifications as a business analyst (BA) in an agile ecosystem is a challenge of a different kind. You no longer have the luxury of time (unlike bigger waterfall projects). You no longer can be sure with a specification version as the final document (because of the iterative philosophy). You are not sure how comprehensive the functional specification should be (Agile manifesto: working software over comprehensive documentation).
</description> 
    <dc:creator>anand.pushkar</dc:creator> 
    <pubDate>Mon, 15 Mar 2021 00:11:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5800</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5730/The-Secret-is-in-the-Wings.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5730</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5730&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>The Secret is in the Wings</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5730/The-Secret-is-in-the-Wings.aspx</link> 
    <description>I could not help but observe in awe the agility of this monstrous wing. My mind could not stop analyzing how an airplanes uses the agility of its wings to control the pressure of the air that flows through them and manipulates the latter to enable it to navigate its journey into the skies. &amp;nbsp;The aeroplane does not change the physical or scientific formation of the air, but it changes its wings to adapt to this natural phenomenon. How intriguing. Adaption. Agility.&amp;nbsp;
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Sun, 29 Nov 2020 11:02:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5730</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5621/Top-Metrics-for-measuring-Agile-Projects-success.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5621</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5621&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Top Metrics for measuring Agile Project’s success</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5621/Top-Metrics-for-measuring-Agile-Projects-success.aspx</link> 
    <description>Good news is that the adoption of an agile approach is increasing with more and more projects being successful. As a business analyst / project management professional, it is important to understand how success is measured for Agile projects? What are the key performance indicators and metrics?

In this article, I am going to list down the top metrics for measuring the success of Agile projects/approaches.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sat, 01 Aug 2020 07:37:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5621</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5651/You-have-to-be-mature-to-be-agile.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5651</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5651&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>You have to be mature to be agile</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5651/You-have-to-be-mature-to-be-agile.aspx</link> 
    <description>An agile organization is characterized by having a comprehensive portfolio of optimized business process and business capability maps grouped by their role in value creation for the customers and support of the business strategy.&amp;nbsp; These maps are linked to all the other disciplines such as finance, governance, resource management, talent management, and customer experience.&amp;nbsp;&amp;nbsp; Thus, Corporate IP can be securely delivered to the point of need.&amp;nbsp;
</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Sun, 19 Jul 2020 16:24:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5651</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5617/Design-Thinking-in-a-Waterfall-World.aspx#Comments</comments> 
    <slash:comments>2</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5617</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5617&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Design Thinking in a Waterfall World</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5617/Design-Thinking-in-a-Waterfall-World.aspx</link> 
    <description>As much as we like to think we are now in a dynamic and agile world, most delivery initiatives are still some shades of agile and all shades of waterfall.&amp;nbsp;These initiatives could have adopted an agile outlook and naming convention, but the businesses they support are often still predominantly waterfall &amp;ndash; going from one clearly defined task to another until realizing value. Think for example, order to cash, just in time logistics etc.</description> 
    <dc:creator>oluwakorede</dc:creator> 
    <pubDate>Sun, 21 Jun 2020 13:00:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5617</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5604/A-Practical-Guide-to-Transition-from-Waterfall-to-Agile.aspx#Comments</comments> 
    <slash:comments>2</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5604</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5604&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>A Practical Guide to Transition from Waterfall to Agile</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5604/A-Practical-Guide-to-Transition-from-Waterfall-to-Agile.aspx</link> 
    <description>The transition from Waterfall to Agile is never easy &amp;ndash; especially for a business analyst who must go through this journey. This document has come about because of this challenge and as an attempt to present a practical guide of how to effectively transition over as a business analyst, and where are these worlds connected. I do not believe that all that we learned as business analyst in the waterfall era are completely useless. What has changed in the Agile world is how we think about analysis, how we present the requirements to our business and our development and testing teams. It is by no means a comprehensive and one size fits all document. But it does provide a start and a guide for those who sometimes cannot make the connection.
Using one fictitious&amp;nbsp; &amp;lsquo;User Story&amp;rsquo; in the Agile section of this document, I provide concrete examples of how and when to present just enough information, while giving your audience sufficient understanding of what they need to bring the requirements to life.</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Tue, 26 May 2020 02:44:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5604</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5528/Knowledge-First-IT-Last.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5528</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5528&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Knowledge First, IT Last</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5528/Knowledge-First-IT-Last.aspx</link> 
    <description>&amp;nbsp;
Step one is get knowledge, step two: redesign for effectiveness then, lastly, step three, pull in IT. It is to start from a base of knowing what IT can do to support a more effective design, the costs of development drop to tens of thousands and everything developed gets used &amp;ndash; an amazing feat in IT development. And the benefits delivered by the IT system are significant: Real-time visibility of the work, accurate information about demand and activity times, costs and materials employed.</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 26 Jan 2020 23:56:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5528</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5515/Is-Agile-Business-Analyst-a-Myth-or-a-Reality.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5515</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5515&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Is Agile Business Analyst a Myth or a Reality?</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5515/Is-Agile-Business-Analyst-a-Myth-or-a-Reality.aspx</link> 
    <description>Have you heard of agile business analyst? Does this even make sense? Agile is to move quickly. How can a business analyst move quickly when (s)he is loaded with effort of understanding the scope, collecting, analyzing, and defining requirements, convincing and negotiating with stakeholders, make a technical team understand the requirements and ensure delivery as committed?</description> 
    <dc:creator>Nimil Parikh</dc:creator> 
    <pubDate>Mon, 30 Dec 2019 16:30:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5515</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5430/Human-Face-to-Enterprise-Architecture.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5430</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5430&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Human Face to Enterprise Architecture</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5430/Human-Face-to-Enterprise-Architecture.aspx</link> 
    <description>If we look at the previously proposed process end to end, it starts with the customer journey. The journey is mapped to the internal business processes, systems, and data sources. For both the customer facing and internal parts of the journey user stories are created to document the gaps between the as-is and to-be states - effectively form the backlog for the change. For each story, acceptance criteria are prepared in a way that enforces the expected behaviour in the system. Ideally, those should be the scenarios that are likely to appear on the real life journeys and not the hypothetical future scenarios. These scenarios when implemented and tested feed back to the journey and underlying layers changing them as the new functionality is introduced.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 17 Nov 2019 09:08:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5430</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5470/Is-there-a-role-for-a-business-analyst-in-an-Agile-environment.aspx#Comments</comments> 
    <slash:comments>5</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5470</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5470&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Is there a role for a business analyst in an Agile environment?</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5470/Is-there-a-role-for-a-business-analyst-in-an-Agile-environment.aspx</link> 
    <description>This question has been asked several times before, and various answers have been advanced to settle this matter. A short answer is &amp;lsquo;Yes&amp;rsquo;. But, unfortunately, this answer is not good enough to the &amp;lsquo;naysayers&amp;rsquo;, who think a business analyst has no place in Agile teams.&amp;nbsp;&amp;nbsp;To answer this question in a long way, we have to take the bull by its horns and talk about the elephant in the room. This article is an attempt to contribute to this ongoing debate. Whether you agree with me or not (as I tackle this elephant in the room), the truth is - this argument is apposite and has to be had.</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 10 Nov 2019 22:22:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5470</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5462/Whats-Missing-from-Agile.aspx#Comments</comments> 
    <slash:comments>5</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5462</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5462&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>What’s Missing from Agile?</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5462/Whats-Missing-from-Agile.aspx</link> 
    <description>John Seddon launches an attack on the value of Agile as practiced and charts a better way to analyse and design for improvement, making information technology the last thing to be concerned with, not the first.</description> 
    <dc:creator>adrian</dc:creator> 
    <pubDate>Sun, 20 Oct 2019 18:48:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5462</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5359/Six-Estimation-Safety-Tips.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5359</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5359&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Six Estimation Safety Tips</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5359/Six-Estimation-Safety-Tips.aspx</link> 
    <description>Estimation is a chronically thorny issue for software practitioners. Most people need to prepare estimates for the work they do, but in our industry we don&amp;rsquo;t do a great job of estimation. In this article I offer six safety tips to keep in mind as you prepare estimates for your project and for your individual work...&amp;nbsp;These six safety tips might not help you create estimates that all of your customers, managers, and coworkers will dance to, but at least they will help you and your team hear the same music.</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 13 Oct 2019 23:05:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5359</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5429/Build-Requirements-Around-Real-Journeys.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5429</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5429&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Build Requirements Around Real Journeys</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5429/Build-Requirements-Around-Real-Journeys.aspx</link> 
    <description>Let us look at it from a different angle now and derive the requirements out of the customer journeys.&amp;nbsp;&amp;nbsp;It is impossible to introduce a change... if the change is big and you try to implement it in one go.&amp;nbsp; This is the reason we tend to break any solution into smaller components. Each solution component should be small and independent enough to be changed individually in a controlled manner. So that eventually we will compose a new experience out of them. Pretty much like using a set of Lego blocks.</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 22 Sep 2019 21:50:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5429</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5315/The-Core-Question-about-Building-Better-Software.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5315</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5315&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>The Core Question about Building Better Software</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5315/The-Core-Question-about-Building-Better-Software.aspx</link> 
    <description>In recent years, agile software development has been the classic example of this pursuit of magic solutions, so I&amp;rsquo;ll use that as an example here. Over the years, though, people have leapt onto the bandwagons of numerous new software approaches. They all have merits, they all have limitations, and they all need to be applied to appropriate problems.</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 14 Apr 2019 08:39:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5315</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5292/What-is-DevOps.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5292</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5292&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>What is DevOps?</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5292/What-is-DevOps.aspx</link> 
    <description>
DevOps is based on a culture of trusted partners. This partnership is between software development, quality assurance, security and controls, and operations. The result is a smooth and fast transition of software from development to operations. However, like Dover, if the trusted partners are somehow reorganized into formal handoffs each with their own software acceptance procedures, the movement of software is no longer smooth nor fast.
</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 24 Mar 2019 22:00:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5292</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5271/How-To-Build-Right-Product-Backlog-Structure.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5271</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5271&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>How To Build Right Product Backlog Structure</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5271/How-To-Build-Right-Product-Backlog-Structure.aspx</link> 
    <description>	In this article, I want to share my knowledge on how to manage product backlog using Jira. The article will be useful not only to business analysts or product owners but also to scrum masters, project managers. Basically, anyone who works with backlog and requirements on a project will benefit from reading it. There are certain rules and approaches that you have to follow to achieve good results.
	Before we take a look at it I want to point out that this approach is not a market standard yet. However, over the last 3 years, I&amp;rsquo;ve completed a good number of projects using the approach I&amp;rsquo;ll be describing here
	On the image below I tried to emphasize the main activities and processes that should be presented in your project. You also have to keep in mind that each artifact and process has own goal and definition.</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 03 Mar 2019 20:52:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5271</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5206/Five-Trends-in-Business-Analysis-Project-Management-and-Agile.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5206</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5206&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Five Trends in Business Analysis, Project Management, and Agile</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5206/Five-Trends-in-Business-Analysis-Project-Management-and-Agile.aspx</link> 
    <description>For almost 10 years we have enjoyed reflecting on what&amp;rsquo;s happened the previous year and making predictions for the upcoming year in the realms of Business Analysis, Project Management, and Agile. Some of the recent trends we have discussed: The digital BA, Lean business cases, BAs and PMs in a Dev Ops environment, BAs and PMs in the gig economy, etc.&amp;nbsp; Here are five industry trends that we have chosen for 2019:...</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 06 Jan 2019 21:40:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5206</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5196/Adding-Value-as-an-Agile-Business-Analyst.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5196</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5196&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Adding Value as an Agile Business Analyst</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5196/Adding-Value-as-an-Agile-Business-Analyst.aspx</link> 
    <description>As more organizations move toward agility, development and project management teams still struggling to define a common language and standard regarding the agile framework. In addition, many organizations that are implementing agile approaches have not fully planned the transition and are still unclear on how to fully optimize the approach. One area that continues to remain vague is the role of the business analyst (BA). Below are some steps to help business analysts navigate their way through the transition to agile and add the most value to their agile teams.</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 09 Dec 2018 20:25:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5196</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5161/Embrace-Gamestorming.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5161</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5161&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Embrace Gamestorming </title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5161/Embrace-Gamestorming.aspx</link> 
    <description>First of all, let&amp;rsquo;s get this out of the way. Gamestorming is not new. Gamestorming is a collection of &amp;lsquo;games&amp;rsquo; put together under the banner of &amp;lsquo;gamestorming&amp;rsquo;. As a business analyst (BA) I can assure you there will be many games in the book and on the website, that you have used in your role under different guises.&amp;nbsp;
Dave Gray (co-author of &amp;lsquo;gamestorming&amp;rsquo;) put it best when he described himself and his fellow authors as the Grimms brothers. The Grimms brothers, if you are not familiar with them- they brought together different fairy tales and published them in a book.</description> 
    <dc:creator>BusinessAnalysisHub</dc:creator> 
    <pubDate>Sun, 18 Nov 2018 14:19:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5161</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5104/Lean-Agile-Bath-Remodel-Project.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5104</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5104&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Lean-Agile Bath Remodel Project</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5104/Lean-Agile-Bath-Remodel-Project.aspx</link> 
    <description>The purpose of this article is to cite an example of using Lean-Agile project management for a small home construction project &amp;ndash; a bathroom remodel. The remodeling firm unknowingly uses a Lean-Agile project approach that was the result of lessons learned over years of experience. In fact, when I questioned the remodeling firm about Lean-Agile, the firm&amp;rsquo;s response was &amp;ldquo;What is that?&amp;rdquo; Regardless of what you call it, the firm uses their construction approach because it works.</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 12 Aug 2018 22:08:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5104</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5034/Make-your-work-visible.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5034</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5034&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Make your work visible</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5034/Make-your-work-visible.aspx</link> 
    <description>When speaking to a business analyst on a busy project, I am often told that &amp;lsquo;at the end of a working day, I feel like I have achieved nothing&amp;rsquo;. Even, though we may feel like that but when looking back on the day you will see that you have probably carried out invisible work. Invisible work is a concept that is frowned upon within the agile world but it is something that we are all guilty of doing. In this post, we look at what the key blockers, which can slow your workflow and why working in visually will help you overcome these blockers. By making your work visible you can reduce the amount of time you waste in a day and be able to do things that you like to do.</description> 
    <dc:creator>BusinessAnalysisHub</dc:creator> 
    <pubDate>Tue, 22 May 2018 14:56:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5034</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5035/An-Introduction-to-Design-Sprints.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=5035</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=5035&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>An Introduction to Design Sprints</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/5035/An-Introduction-to-Design-Sprints.aspx</link> 
    <description>Naturally, us Business Analysts are facilitators, whether we&#39;re running workshops or holding stakeholder meetings, we&#39;re always the ones engaging with people. And it should really be no different for the running of a Design Sprint; use your best facilitating skills to lead the Design Sprint and make it a really good week for everyone involved! In addition to hosting over the five days, you should consider yourself responsible for reporting on the outcomes of the week to stakeholders, this will include making a decision on what to suggest taking forward as an idea and what should simply be forgotten about.</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 13 May 2018 21:30:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:5035</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/4924/Kanban-vs-Scrum.aspx#Comments</comments> 
    <slash:comments>1</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=4924</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=4924&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Kanban vs. Scrum</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/4924/Kanban-vs-Scrum.aspx</link> 
    <description>Efficient and smooth workflow practices are believed to be accomplished through Agile methodologies with an emphasis on flexibility and rigor to optimize utilization of resources. Two popular implementations of Agile are Scrum and Kanban. In would be fitting to compare and analyze these processes, in an attempt to understand the dynamics behind their respective methodologies.</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Sun, 22 Apr 2018 19:04:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:4924</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/4993/Top-3-Activities-for-a-Business-Analyst-in-a-Discovery-phase.aspx#Comments</comments> 
    <slash:comments>2</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=4993</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=4993&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Top 3 Activities for a Business Analyst in a Discovery phase</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/4993/Top-3-Activities-for-a-Business-Analyst-in-a-Discovery-phase.aspx</link> 
    <description>
In at the deep end

So, you&amp;rsquo;ve just heard you&amp;rsquo;re going to be the Business Analyst on an Agile team that&amp;rsquo;s going in to a Discovery and it&amp;rsquo;s your first one. &amp;nbsp;For my first Discovery, it was daunting let me tell you. I already knew quite a few tools and techniques a BA should use during the lifecycle of a project, but what ones do I use that are particular to a Discovery phase?
For this blog, I interviewed other Business Analysts, Scrum Masters, Product Owners and Developers to get their view on what the role of the BA is in Discovery and I will use their opinions (along with mine) to provide what I think are the top 3 tasks a BA should carry out.

Time is of the essence

You may be thinking, &amp;lsquo;surely you just apply the right tool or technique for the situation?&amp;rsquo; Good question and I would say this is true. However. Unlike a traditional project where the BA would investigate, analyse and document literally everything, in Agile, Discovery phases are given quite a short amount of time before moving to Alpha and this is where as a BA (along with the rest of the team), you need to use your time wisely as you just won&amp;rsquo;t have the time to do all those &amp;lsquo;traditional&amp;rsquo; BA activities.
Now, there is a process to follow in that you can&amp;rsquo;t start to create a backlog until you know what the user and business needs are, and you can&amp;rsquo;t find out those needs until you identify your users and stakeholders. So, this is where we&amp;rsquo;ll start.

Stakeholders: Don&amp;rsquo;t just identify, analyse

The top activity the other roles identified as a key role of the BA was to understand and define the problem. However, before we get to that stage, we need to identify our stakeholders and users. And perhaps more importantly, understand the stakeholder&amp;rsquo;s interest and their influence in your project.
For me, this is a critical exercise that I don&amp;rsquo;t feel is given the importance it should at the start of a project. They either get done and are left static throughout the project or not done at all.
While the BA might lead on this activity, it&amp;rsquo;s most definitely an exercise the whole team need to be part of. My tip here is to put a stakeholder interest/influence matrix on the team wall (hopefully you have one, if not, get some whiteboards!) and give yourself and the team a couple of hours for the session. There are plenty of templates online you can use or if not, just draw it on some flipchart. Give the team around 10-15 minutes to identify who they think are stakeholders and begin to plot them on the matrix.&amp;nbsp;
There may be some conflict where these people sit on the matrix but as long as you agree on who are the highly influential or clearly fit in to a category, the borderline ones you can leave for now.
In terms of analysis and potential time constraints you have, don&amp;rsquo;t go in to any particular detail and spend time creating stakeholder wheels or stakeholder management plans, the interest/influence grid is sufficient. In addition, use the matrix to create your communication strategy to define what methods you will use to show progress of the Discovery to stakeholders and how often you will communicate with them.
For identifying users, this will be something the User Researcher will lead on as they will be interviewing them but you as the BA should be involved in those sessions. After all, if you are going to be writing the user stories based on their needs, you need to get this first hand. You will also pick up good interview techniques from the UR.

Framing the problem to define scope

Ok, so we now have a list of stakeholders and users and it&amp;rsquo;s time to start engaging them. Before you start looking at things like defining &amp;lsquo;as is&amp;rsquo; processes, pain points and setting up interviews with stakeholders to get this information, you need to have an understanding of what the actual problem is the team has been put together to fix.
You may have been given a mandate as to what the issues are but until you engage the people &amp;lsquo;at the coal face&amp;rsquo;, they are just perceived issues. The quickest way to get to the root causes is to get those key stakeholders in a workshop and identify the following:
&amp;middot;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Why are we doing this work?
&amp;middot;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Who are our users, clients and stakeholders?
&amp;middot;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; What outcomes might users get from this?
&amp;middot;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; What outcomes might the organisation get from this?
&amp;middot;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; What are our key metrics?
Now, a lot of information will come out of this session and I see the key role of the BA is to deconstruct all these thoughts and views and turn it into something meaningful&amp;hellip;&amp;hellip;like a problem and a product vision statement.
These statements are short and provide an overview of the vision, problems and methods the team will use to address them. It should be no more than a few sentences which is a difficult task and one I suggest should be collaborated and created with the rest of the team.
Once you are all happy with it, you need to share it with the stakeholders. Not to get agreement or for endless reviews, but to ensure everyone is on board with what the team are trying to achieve.
As some (maybe most) stakeholders may not be aware what a problem and vision statement is, you may have to spend some time explaining its purpose to them. Point out it&amp;rsquo;s not a personal view, but a collective interpretation of perceived issues that need addressing.

The backlog

As with defining scope, starting a backlog of user stories is not solely the responsibility of the Business Analyst but is something the team are responsible for and should contribute to. That said, the BA does play a critical role in the creation of a backlog. And that is to ensure that what goes in to it is of an acceptable standard. After all, rubbish in, rubbish out right?
I&amp;rsquo;ve seen this so many times whether it be on a new product or one that has progressed in to Alpha and Beta where the backlog has become a bit of a dumping ground for every idea, whim or &amp;lsquo;wouldn&amp;rsquo;t it be good if&amp;rsquo; thought.
For a start, everything in the backlog should either be related to a user need or part of the product roadmap. If it doesn&amp;rsquo;t, it shouldn&amp;rsquo;t be there. If someone does have an idea worth further exploration, put it on the user research/UX hypothesis board so they can establish whether there is an actual need for it.
Before you start creating a backlog, get the team together to agree ground rules. I suggest you hold a user story writing workshop with the team where you can begin outlining the backlog. This ensures the team are involved from the start and you can agree principles with them to stay clear of the &amp;lsquo;bloated backlog&amp;rsquo;.

Who might I be working with in a Discovery team?

Discovery teams can be made up of several roles, most commonly; a Product Owner, User Researcher, Business Analyst(s), Subject Matter Experts (SMEs) and a Scrum Master/Delivery Manager
I&amp;rsquo;ve worked on Discoveries where a Scrum Master/Delivery Manager wasn&amp;rsquo;t part of the initial team and I found the focus and cohesion of the team became lost at times due to a lack of discipline in setting and achieving targets (i.e. sprint planning).&amp;nbsp; When time is the key factor, the team needs to stay focused on its goals which I think the Scrum Master brings.
You&amp;rsquo;ll start to get the impression now that the Business Analyst is not really &amp;lsquo;solely&amp;rsquo; responsible for the outputs of a Discovery but is involved in all of them. One of the people I interviewed for this blog explained his view of the role of the BA in a great way. He said they are &amp;lsquo;decoders&amp;rsquo;. By this he meant they translate all the information gathered (and there will be a lot of it) in to outputs that not only the team understand, but any stakeholders.
I believe this is the primary role of the BA however in an Agile Discovery, you should be able to evaluate what you are doing is of value and that you&amp;rsquo;re not just &amp;lsquo;going through the motions&amp;rsquo; because of pre-defined duties of the Business Analyst.
I hope this has been helpful and that if you are asked to join a Discovery team, you are equipped to get engaged in those top key deliverables to make the Discovery a success.&amp;nbsp;


Author:&amp;nbsp;Nick Stowers,&amp;nbsp; Business Analyst
As a BA for nearly 5 years now, I&amp;rsquo;ve come to realise the role of the BA is still misunderstood in business and I hope to provide readers with insights how a BA brings value to organisations that are using an Agile framework to deliver their products and services.&amp;nbsp;&amp;nbsp;I want to inspire current and future Business Analysts that they are the cornerstone of project teams to deliver products and services that are focused on the user and bring creativity, innovation and value to people. 
</description> 
    <dc:creator>nickstowers12301</dc:creator> 
    <pubDate>Sun, 15 Apr 2018 09:12:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:4993</guid> 
    
</item>
<item>
    <comments>https://modernanalyst.com/Resources/Articles/tabid/115/ID/4982/Why-you-need-Lean-Business-Analysis-LBA-for-more-successful-products-and-services.aspx#Comments</comments> 
    <slash:comments>0</slash:comments> 
    <wfw:commentRss>https://modernanalyst.com/DesktopModules/DnnForge%20-%20NewsArticles/RssComments.aspx?TabID=115&amp;ModuleID=572&amp;ArticleID=4982</wfw:commentRss> 
    <trackback:ping>https://modernanalyst.com:443/DesktopModules/DnnForge%20-%20NewsArticles/Tracking/Trackback.aspx?ArticleID=4982&amp;PortalID=0&amp;TabID=115</trackback:ping> 
    <title>Why you need Lean Business Analysis (LBA) for more successful products and services</title> 
    <link>https://modernanalyst.com/Resources/Articles/tabid/115/ID/4982/Why-you-need-Lean-Business-Analysis-LBA-for-more-successful-products-and-services.aspx</link> 
    <description>Customers are demanding better service and they know they can get it and BAs have a duty to provide it through Lean Business Analysis (LBA). Not because customers see better service from a business&amp;rsquo;s competitors. But because they get it from all the other companies they interact with in their daily lives as consumers of Uber and Apple and Amazon and Netlfix and many more. They don&amp;rsquo;t care that one company is a bank and Uber&amp;rsquo;s an app.</description> 
    <dc:creator>Transform VA</dc:creator> 
    <pubDate>Tue, 10 Apr 2018 04:20:00 GMT</pubDate> 
    <guid isPermaLink="false">f1397696-738c-4295-afcd-943feb885714:4982</guid> 
    
</item>

    </channel>
</rss>